I have two SSRS 2005 Reports, we'll call them "Report A" and "Report B." Report A has 2 parameters, with the first being a single-value dropdown and the second looking up available values dependent on what's chosen from the first parameter. Report B is very similar except it has 3 params, with the 3rd being dependent on the first 2 single-value dropdowns. In both cases, the last, dependent parameter is multi-value with a default value that is guaranteed to be there (the SQL looks like select 'ALL' union select .... ). Ok so here's the problem. For Report A, when the first param is chosen, the second becomes available with the default value of ALL preselected, which is good. For Report B, when the first two params are chosen, the 3rd param becomes available but the default value of ALL is NOT preselected, which is bad. I don't see the same issue when I go at the report with the web viewer (meaning both reports prepopulate the last param with the default value). To me this suggests a bug with the WinForms ReportViewer. To illustrate that the problem has to do with the last param depending on more than one param, I changed its SQL to only depend on the first param (but the 2nd param was still on the report). When I tried that, the last param would correctly get its default value when the first param was populated. I've tried adding a hidden parameter "between" the last param and the first two params on Report B that simply smashes both values from the first 2 params together and making the last param use that new param instead, but that doesn't work either (same behavior: it becomes available but doesn't get prepopulated with the default). The new "between" param gets filled in with the correct combination of the first 2 params, which I assume worked because it's not multi-value like the last param is. To me this seems strange, as the last param is in fact now dependent on a single parameter. Has anyone else run into this issue? If so, is there a workaround? Thanks in advance!

Hi Schrag4, To this issue of yours, it seems a bug, so I would recommend you to submit a feedback to Microsoft Connect at this link at this link https://connect.microsoft.com/SQLServer/Feedback This connect site is a connection point between you and Microsoft. Your feedback enables Microsoft to make software and services the best that they can be, Microsoft might consider to add this feature in the following release. Currently, if this issue are urgent to your business, you could also contact Microsoft Customer Support Services (CSS) via telephone so that a dedicated Support Professional can assist you in a more efficient manner. However contacting phone support will be a charged call. but it will be free if this is a product issue. To obtain the phone numbers for specific technology request please take a look at the web site listed below. http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS Thanks, Challen FuPlease remember to mark the replies as answers if they help and unmark them if they provide no help.